Search Results: "bruno"

28 December 2009

Luca Bruno: Uzbl in Debian


After some delay, uzbl is now available in Debian (testing and unstable). Uzbl is a webkit based browser which aims to adhere to the Unix philosophy of having programs that do one thing and do it well; as such, it comes with a main binary (uzbl-core), acting as the real web-renderer, which is controllable by third-parties via standard fifo s and sockets. The package also bundle some external helper scripts for daily web-surfing (ie. handling history, bookmarks, cookies, etc.) and a ready-to-user wrapper (uzbl-browser) to help setting up the environment, using the default config.
As a standalone browser, it may look quite similar to vimperator (default key-bindings and interface are strongly vim-like), but overall it offers a more powerful and completely reconfigurable user-interface, can be fully scripted and hooked with self-made helpers and is even embeddable in other applications (eg. Emacs). Nonetheless, it brings all the power of a fully fledged webkit renderer. You may find it particularly useful when working within a tiling window manager (like awesome or xmonad), or used as a full-screen remote monitor, easily controllable via socket (you should really try socat with it!) or plain-text fifo (for a bunch of stats, as easy as a echo "uri italiaora.org" > /tmp/uzbl_fifo_your-instance )

27 November 2009

Sandro Tosi: Reportbug has now less than 150 outstanding bugs!

Yes, finally we made it! Thanks in particular to Carl Chenet and to Luca Bruno we were able to reduce the reportbug bugs count below 150!

It was a very long road (when I joined the team there was 230-something bugs opened) and I hoped to achieve this some time ago, but the fought goals are the most relevant ones.

Of course, the just released version 4.9 contains quite some bug fixes and enhancements: if you have the chance, give it a look and report any regression or feature request you see fit, but not too much: I want to enjoy the barrier just broken :)

26 November 2009

Luca Bruno: Inkscape 0.47 is out!


After over a year of intensive development and refactoring, Inkscape 0.47 is out. This version of the SVG-based vector graphics editor brings improved performance and tons of new features, some of which are as follows: Timed autosave, Spiro splines, Auto-smooth nodes, Eraser tool, New modes in Tweak tool, Snapping toolbar & greater snapping abilities, New Live Path Effects (including Envelope), A huge collection of preset filters, New cairo-based PS and EPS export, Spell checker, Many new extensions, Optimized SVG code options, and much more. Additionally, it would be wrong to not mention the hundreds of bug fixes as well. Check out the full release notes for more information about what has changed, enjoy the screenshots, or just jump right to install it. Release Notes:
http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047

5 May 2009

Luca Bruno: Inkscape 0.47 (tentative) release plan and about-screen contest


Time has come again for a new shiny release of Inkscape, namely 0.47
So Scislac recently published a raw release plan, and we ve already entered the soft freeze period. The stable release is currently due for middle of June, but right now it s a too early stage to fix it on a calendar Meanwhile, we re running the usual about-screen contest, hosted once again at DeviantArt. The contest will be running till May 25th so start working on your sumission right now and have the opportunity to let your signature on this marvelous release! Be sure to check the rules for it first Still a lot of work has to be done, so if you re a bug-hunter (win and and OSX much appreciated), a translator or a documentation writer, feel free to get in touch with the inkscape community and help us make another great release.

12 April 2009

Sandro Tosi: Reportbug 4.1

So it's Easter (if you believe) and what do I do? Instead of fixing this I cut off a new Reportbug release... yay

Several bug fixed, and the thanks goes to:
Have fun!

24 October 2008

Sandro Tosi: Bits from the reportbug side of Debian

Things are evolving under the hood for reportbug, and we are preparing a version targetted for squeeze.

The version 3.99.0 has just been released to experimental; the main goals for this release are:
Other goals we'd like to archive for the 4.0 version (for which 3.99.x are the pre-releases) are:
Since this is a development version, you can experience some bugs/regressions, so please try it, stress it and "reportbug reportbug" if needed :) You're help is really appreciated! (and we have cookies ;) )

18 August 2008

Luca Bruno: kaeso


As Meike mentioned, Debian turned fifteen last Saturday. We enjoyed our Italian DebianDay too, in a sunny and beautiful day, very close to the sea (a great thanks to lug Govonis, here!).
Lots of talks and interesting discussions all the day. with people crossing half Italy to celebrate and party with us, ended with a great pizza all together. A wonderful DebianDay, really :)

10 August 2008

Alexander Reichle-Schmehl: Bits from the DPN editors

It's more or less four months since I proposed to resurrect our newsletter. We already released eight issues of the Debian Project News and work for the ninth issue has already started. So I guess it's time for a small "state of the DPN" speech, but since I'm not attending DebConf, you will have to read this mail instead ;) After having a rough start (and in fact missing some self-set deadlines and completely underestimating how much work is involved in such a kind of newsletter) we finally developed a - more or less - working flow of work (Which is by the way documented here). Speaking of the current state sadly means to confess, that our hopes to draw a lot of help from the community by using a system for drafting the news with a low entry barrier were not fulfilled. We actually had a good start, with good participation, but due to (I assume) the aforementioned initial difficulties participation in the creation of the DPN dropped considerably. Currently the workload of creating our bi-weekly newsletter is shared by only two people (that being Meike Reichle and myself), which is barely enough :( While we at least get a hint from time to time, what we should mention in the next issue, it rarely happens, that someone contributes by drafting a text -- which is the real work. (At this point a BIG "Thank You" to those who did! (See list bellow.) It's much appreciated!) We suffer especially, since although we are a two people team, we have in fact no redundancy, since real live issues affecting one of us will most likely affect the other one, too. Therefore we mostly concentrated our work on creating the next issues and getting them out in time, and didn't have time to answer all mails considering suggestions for changes and improvements (yet?). We are sorry, but at least we tried to read them briefly and keep them in mind when drafting the next issue. As a result of this we re-added the list of DSAs, WNPP and new and noteworthy packages due to popular demand. There are still a lot of unanswered mails not dealing with content, but with workflow issues / proposals (including changing from wiki.debian.org to a special ikiwiki instance). We are sorry, that we couldn't yet act on them and take appropriate measures, but be assured, they are not forgotten. Other issues the DPN currently have are "unwritten guidelines" regarding editorial choices of DSAs to be published and which packages to list in the "new and noteworthy package" section. Both is more or less done by our gut feeling. Speaking of problems the DPN are facing, we also need to mention translations of the DPN. The current workflow makes it difficult for translators of the DPN, since we often fail to get the final draft of the DPN ready in time to give translators a "head start" so the translated DPNs can be released together with (or at least with a as small as possible delay to) the English DPN. So here is a big call for help! We really need your help writing the DPN. (Monitoring lists and newstickers we don't monitor ourselves would be nice, too, but only add more work to us if you only give us pointers.) We will both be very busy with our real live the upcoming month, and are not sure how much time we can dedicate to the DPN. So please help us! The current draft for the next issue of the DPN is always available here . There should already be a todo list with pointers to interesting topics, which need to be written out. Some guidelines about style and content are available here. Last but not least, we would like to thank the following people who have contributed to the DPN so far: (Unfortunately we can't list those people, who contributed by translating the DPN, nor do we have a complete list of the native English speakers, who helped by proofreading. But we thank them nonetheless!)

30 April 2008

Luca Bruno: kaeso


Some of you may have already read of ksplice, a recently announced hot-patching system for Linux kernels. Given the actual kernel source tree and a security patch to be applied (which shouldn’t include semantic changes), it can build a kernel module with the fix which would introduce a trampoline to the bug-fixed object. The mechanism, along with other limitations, is described more deeply in the accompanying paper. An RFP was reported a couple of days ago, for which I’ve put an initial rough packaging under collab-maint with git (both source package and i386 binary are already available). All the things are still a bit unripe, thus before allowing it into unstable I’d like to find a co-maintainer (preferably with a good kernel knowledge :) ). So, if you found it useful and want to help, feel free to drop me a note.

25 March 2008

Luca Bruno: Inkscape 0.46 released


The Inkscape community is really proud to announce the release of the newest version of its open source vector graphics editor: Inkscape 0.46 is out!
This version introduces a lot of new features and various improvements, and I’d suggest you to read the release notes.
Binary packages for most common platforms will be available soon.
Inkscape 0.46 released
Kudos to all the members working to keep Inkscape rocking!

23 January 2008

Luca Bruno: Nemiver in experimental


A lot of new features were recently added to nemiver, a new and promising standalone graphical debugger for GNOME. Jonathan and Dodji announced a shiny new global variables watcher and an impressive hex memory viewer/editor, based on gtkhex widget. However, before being able to release the next stable version, they need a lot of testing and bug-hunting: so I’ve just uploaded a recent SVN version to experimental. Please test and report any bug not yet reported.Also, note that upstream contributors are always really welcome, and that there is also plenty of non-coding work to do, as documentation and translations are still in progress…

6 November 2007

Wouter Verhelst: Programming languages suck?

Bruno De Wolf blogs about programming languages. His statement: "all programming languages suck". Not sure whether I agree. But's let look at his arguments. In his words, a good programming language, among others, is readable by a guy who didn't write the original program and who doesn't know all the language details or libraries. Personally, I don't agree. Code readability, above all, depends on the programmer. Programming languages that impose structure can probably help, but it's possible to create unreadable code in any language—that doesn't need goto. Since I went to the 'karel de grote' institute of higher education, I learned quite a number of programming languages. Hairy code is possible with all of them. Unreadable code is easy with some of them, and some of those I do consider good programming languages. I guess my criteria are different: That's it, I guess. In my book, a programming language is a tool to get a job done. A good tool is flexible, not too unwieldly, and somewhat intuitive. Like a hammer. If you want to build a table, you probably need a hammer, among other things. The better the hammer, the more likely it is that you'll get a nice table. But even the best hammer won't get you a wonderfully crafted table if your carpenter sucks at his craft. And so it is with programming languages: it might help if you use a proper language, but any good programmer can write readable code in any programming language.

5 March 2007

Ross Burton: Tasks 0.3

Tasks 0.3 is out! The main new features are internationalisation and category filtering. A complete list of user-visible changes: I also had a few translations: Sources are available on the OpenedHand Projects site, and packages for Ubuntu Edgy, Ubuntu Feisty, and Debian Sid are in my repository. Adam Williamson has also packaged Tasks into Mandriva Contrib.

Andree Leidenfrost: IA64 Support for Mondo Rescue!

The first fruit of my work on Debian IA64 packages for Mondo Rescue are now on http://people.debian.org/~andree/packages/. It took a bit longer than I had anticipated and there was a bit of an interruption while I stayed on beautiful Norfolk Island for two weeks.

Everything should be fine and dandy apart from the fact that restores will currently miserably fail on IA64 because parted2fdisk expects an older version of parted than what Etch and Sid contain.

So, why publish IA64 packages at all if they don't even work, I hear you scream. Well, firstly I thought I give a bit of an update and show that things are actually moving forward. Secondly, maybe I'm lucky and someone is interested in helping out with getting parted2fdisk to work with newer versions of parted or (better) in getting mondo migrated to using parted natively on all platforms (pending Bruno's approval).

Other than that, the packages have a few user-visible improvements and fixes across all supported architectures and they bring the Debian packages a fair bit closer to upstream - see the changelogs for details.

As usual, check out the new packages, let me know if something doesn't (or does) work, get involved! ;-)

15 February 2007

Biella Coleman: I cite, you cite, I rant

Since there are few topics about academic etiquette than get me as excited as the norms of citations, I was quite fascinated by Joseph Reagle’s blog entry on the topic, a discussion that spanned a summary of Helen Nissenbaums’ work on the subject to his own wrangling with how he should recognize others who have independently reached similar conclusions as his own. Citations fascinate me because they are one of the few tangible inscriptions that reveal just how much of our work is indebted to others; it is stimergic (and if you don’t know what that is, read Joe’s entry as his moral wrangling over citations had to do with this term, his use of it and the discovery that someone else came up with it also). Despite the fact that all disciplines use them, we use them slightly distinctly. Lawyers use them in lawyerly-like ways: they cite the crap out of everything (it is kinda annoying but kinda helpful) and this makes total sense: they are covering their asses (lawyers know how to do this well), they are following the logic of their own practice as case law is quite citational, and well, law professors usually have one if not two research assistants, and this I am sure helps them in covering their citational bases. Another big difference in practices of citations is between a conventions that includes the name of the person you are citing in the body of the text and those that stuff all that data in a footnote. I can’t stand the later convention, not only because it is a pain in the neck to have to go back to the footnote JUST to see who the heck the author is citing but I think the credit should be right there, springing off the page so that the politics of collaborative recognition are, well, very evident (and I do understand that if you are citing a buttload of folks, that sometimes it is just better to do that in footnotes and sometimes with history they are citing way to may folks to really do it effectively in the body of the text). Joe raises some fundamentally thorny questions of who and how do we cite given that we may come up with an idea with the power of our own little brains, only to find out (gasp) that others, past and present and very unknown others, say something similar. On the whole, I tend to try to make clear, as Joe did in the example he provided, where I am totally taking the idea from someone to apply to another idea of mine and where I have an independently crafted idea and I am citing others so as to support my own position, which usually only strengthens my own argument. And what I find is that just because a cohort of folks may be working on similar topic (open souce, hackers), since we do so from our own perspectives and methods, most of the research will be original, though not as much as we tend to perform to our superiors. Also I sometimes find myself with an idea, which I consider as my own, but where I am so in need of a citation because it is an idea that seems at an intuitive level to be right on but it is hard to truly substantiate with the data I have (I am in that position right now and am desperate to find someone who says what I say and thus have a means to support what otherwise seems like a lofty idea…) And in fact, one thing that bothers me about citations is that we don’t seem to take seriously that the date of publication may not just tell us when something was published but help us gauge if something can become “dated.” What I mean is that when (and I guess if) I publish my book on hackers and Debian, it will not be a reflection not of some timeless aspects of hacking but firmly based out of the time period (roughly 10 years give or take 3 or 4) that I was either researching and writing about the topic. And while you can and should cite folks who wrote stuff in the past because that stuff still matters (a lot of what Steven Levy says for example still holds water) a lot changes. And yet I can’t stand how folks then cite someone as wrong when in fact all that went wrong is that time does what it does best: MOVE FORWARD and social phenomenon change along with the passing of new moons. This is not as likely to happen in the hard sciences but sure as heck happens with anything in the so-called human realm (which is why it bothers me that the social sciences and humanities model our citational and journal practices so similarly to the hard sciences, when it seems there are enough differences to warrant more differences than there are but that is a whole other topic). So now I try to note where my analysis diverges because the context so radically changed and really leave critique for those things I can safely and fairly disagree with on its own terms.
Finally, Nissenbaum’s article seems so interesting (I have not yet read it but now will) because it confronts how our practices of citations may or may not (or should) change in the face of a proliferation of access to work due to electronic media (she flags: wildcat publisher, grey literature, preprints). But I have found that, at least in anthropology journals, and especially in the anthropology of science, technology, and medicine, authors are mostly citing other anthropologists, as if a whole scholarship on a topic was non-existent, which seems more odd today when it has gotten easier to mine and find this stuff. They only cite “non-anthro others” when these folks are so standard, it would look horrible not to do so, but there is not a move to branch out, which I find a real shame and why I sometimes get really down on disciplinary journals (and why I am quite content to be joining an interdisciplinary department). And to be clear, I don’t fault individual authors, it seems that this is the unstated expectation and if that is what is going to get you in a journal, and that is what gets you tenure brownine-points, then you do as everyone else does. And that brings me to the final point which is the problem with standards in citational practices. So for example in the field of science studies, everyone must and usually does cite Bruno Latour. And as Chris Kelty reminded us, there is *very* good reason to. But I find what happens is that once a person is flagged and gets cited ad nauseum (which is mostly a decent but not full proof baramoter for judging good work), it become self-perpetuating reality/cycle because everyone else is doing it and it seems weird if you don’t (and I have sometimes seen some articles just awkwardly cite famous people in their discipline when it made little sense to do because, I think of this phenomenon). So all of a sudden, it becomes all Microsoft-Windows like: you cite, they cite, and it becomes “standard” who you cite and you can’t seem to escape the default. But alas, there is always an escape hatch, because one of the gems in academia is discovering that one theorist or book relate x to y and z topic that for some reason everyone else overlooked (because they were busy citing Latour,) to bathe some topic in a wholly new light and then a whole group of folks become unfashionable and the cycle begins, yet again…. The solution? If we only had a couple of research assistants like the lawyers, well maybe we could branch out a little and cover our bases a little..

1 February 2007

Christian Perrier: Solutions Linux 2007

(update: numerous typos removed) This year, attending the whole Solutions Linux event wasn't compatible with my paid work (for those who care, I'm since September head of the Personal and departmental computing unit in the Networks and Information Department of ONERA, the French Aerospace Lab). Despite this, I booked at least yesterday afternoon to visit the expo and more particularly the Debian booth. It is always a pleasure to meet again French developers and contributors as well as all these old dinosaurs which I learned electronic communications with 1200bps modems with, some time ago. The Debian booth was as crowded as usual. It was still featuring a Babelbox, built in one night by Pierre Habouzit and Julien Blache. Congratulations, you did an awful job here. I'm glad I saw all those good people. I was tempted to cite everybody and will finally refrain because I'm too afraid of forgetting one of you guys. For our international readers, this includes several of the people I may have had a few flamy discussions and even blog "wars" with in the recent past (I'm just missing you, Joss, being told that you couldn't attend that Wednesday). As usual, we all survived very well. The other "big" event was also the first formal meeting of the Debian France non-profit organisation. Everything is pretty young but the hidden creation work done by the founding members has been huge and the base is now here. Debian now officially exists in France. I'll do my best to play my part in this action and work with other members of the board to fit the organisation goals and bring Debian more prevalence in our country. I also had a very long talk with Bruno Cornec and Louis Bouchard from HP. We discussed about HP customers needs for official support for Debian on HP machines, and not only servers (ONERA has an internal project to deploy a few hundreds of workstations aimed at being the scientific platform for ONERA scientists and PhD students. We already have more than 100 of these, based on RHEL and guess what are my mid-term plans for them? :-)). We just need some official commitment from HP to support using Debian to unlock the internal fears. It sounds like HP could go this way if customers show enough interest. Of course, ONERA's project is pretty small but we are one of the key players in out domain in the country so that could be kind of interesting marketing for HP...and Debian..:-). Bdale, I need to talk with you soon.... Back to work now, for a few days. Then, I'll take 3 days off next week to attend the 3rd Free Software World Conference in Badajoz and present the results of the Extremadura i18n session we held in September, along with other people who held some of these sessions, namely Frans Pop (about the D-I session), Wookey (about the Embedded Debian session), Knut Yrvin (about the Debian-Edu session) and Martin Michlmayr (about the QA session). All people who I will be very glad to meet again.

25 January 2007

Andree Leidenfrost: linux.conf.au 2007 Gleanings

I was fortunate enough to attend lca2007 last week and to meet Bruno Cornec, the Mondo Rescue project leader, for the first time in the flesh.

The conference was pretty cool, and I found the quality of the program to be generally impressingly high: Excellent topics, superb presentation skills, humor and genuine passion for the topic at hand. The atmosphere and organisation were great, too - extremely well done, 7 Team!

My personal two highlights were:
Apart from the conference as such, it was super cool to meet Bruno. We had a number of good conversations and did some nice hacking, burning the midnight oil a couple of times. And HP gave me a (used) zx2000 (which Bruno carried all the way from France to Sydney!) to enable me to work on the (Debian) Itanium port of Mondo Rescue - thank you HP and Bruno! Bruno's talk was well received, and it was great to actually meet people that use the software that I spend quite a bit of time on. :-)

Finally, there is the Linus phenomenon (so you can tell this is my first
Linux conference) - he amazingly is basically left in peace: People who know him obviously talk to him and he participates vividly in discussions and so forth, but everyone else does the business as usual thing - no autographs, no photos, no nothing. I was (positively) impressed and refrained from asking him to sign my copy of Just for Fun (just kidding).

Finally, finally, I propose to find an alternative for the term 'awesome' next year. ;-)

14 January 2007

Andree Leidenfrost: Debian Pre-Release of Mondo Rescue 2.2.1, Take 2

mindi-2.21~r1021-2 and mondo-2.21~r1021-2 are now on http://people.debian.org/~andree/packages/ with the following changes:
  • petris works again during restore (self-inflicted, oh well).
  • Restore of ISO images and friends should now work when gzip (i.e. '-G') is used.
  • The network interfaces should be fine now when booting into a restored system for the first time.
Other than that:
  • The crash in mondorestore when nuking from tape has disappeared. I have no idea what caused it or why it went away again, though...
  • Kernel 2.6.18-3-k7 hangs when 'acpi=off' is specified (which is the default as per mindi's ADDITIONAL_BOOT_PARAMS, so restore fails with this kernel). I have filed bug #406809 which may or may not be related to #389931.
  • The issue with booting a (NTFS) Windows partition failing after a restore appears to be normal as per the ntfsclone manpage:
    Usually, Windows will not be able to boot, unless you copy, move or restore NTFS to the same partition which starts at the same sector on the same type of disk having the same BIOS legacy cylinder setting as the original partition and disk had.
  • I have tried a few things playing with parted and ntfsresize, but so far the only thing that works reliably in order to get Windows to boot is resizing the partition using gparted. I still have to figure out what it is that gparted does differently. (If you know, please tell me!)
Off to bed now so that I'm fine and dandy when I pick up Bruno from the airport in the morning for lca2007. :-)

26 December 2006

Andree Leidenfrost: Mondo Rescue Debian News

I've used the Christmas time to do some work on Mondo Rescue:

I've uploaded mindi-2.20-2 which fixes RC bug #403454 and important bug #404315. Luckily, I only had to apply patches provided by Matija & Bruno - thanks guys! I've asked for the new version to be allowed into Etch but haven't heard anything yet (maybe I should have waited a few days first or something?).

Also, I've packaged the new pre-release version of Mondo Rescue. You can grab it from here: http://people.debian.org/~andree/packages/. I would much appreciate feedback on how things are working on Etch. So, if you take them for a spin, please let me know how it went, good or bad! The upcoming new release fixes a substantial number of bugs and comes with some notable improvements, so it should definitely be worth checking out.

Finally, when doing some testing I came across a problem with the stock Debian 2.6.18 kernel when used on a Mondo Rescue recovery media. It sometimes already hangs while booting and sometimes starts the restore only to hang later during formatting or even later during restore. This seems to only happen on i386 whereas amd64 is fine. It may also be restricted to my hardware (although it hangs in Qemu as well). 2.6.17 is fine btw. If anyone has an idea what could be causing this, that would be great as I haven't got the foggiest at the moment (there is no message whatsoever, it just hangs).

9 October 2006

Andree Leidenfrost: New Upstream Mondo Rescue Packages

I have just uploaded mindi and mondo 2.20 (version numbers are now the same for mindi and mondo).

This release marks a bit of a milestone in that we can ship the pristine upstream source in Debian for the first time because the busybox binaries were removed upstream. This together with the numerous bug fixes and stability improvements and combined with the fact that there are no revolutionary new features (despite the version number jump) made me decide to try and push the new upstream version into etch.

'Try' because although I've tested things quite thoroughly on both amd64 and i386, there is always a residual risk (one of my favourite alliterations ;-) ) of something bad slipping through. I think that taking this risk is justified, though, because 2.20 should be a definite improvement over 2.09. Bruno and I worked really hard to get this released in time for etch (Thank you, Bruno, for making my priority your priority!).

While testing, I found #389931, #389729 and #390653 (Thanks for your great help, Russ!). I've also found that archiving to tape doesn't work for me (still gathering more information, so no bug report yet), but it also fails with 2.09, i.e. there is no regression.

Main testing was performed on:
Oh, and this also contains the fix for RC bug #391127.

People seem to be using Mondo Rescue on 'vintage' versions of Debian which is presumably due to Mondo Rescue being disaster recovery software. So, I've made a change to post-nuke suggested by Augustin Amann (Thank you, Augustin!) to make people using the latest packages on sarge happier. I'm still in two minds about adding versioned depends on grep and binutils to make the life of woody (!) users a bit easier as well.

Next.

Previous.